InstallCert.java › CopyOffsetsOfAConsumerGroupToAnotherConsumerGroup › IterableReducer › DateMacro › weblogic_getInitialContext() › Business Rule Engine
- jEdit . . . . 32 matches
options.pmd.rules.EmptyTryBlock=true
options.pmd.rules.AvoidCatchingThrowable=true
options.pmd.rules.EmptyFinalizer=true
options.pmd.rules.LooseCouplingRule=true
options.pmd.rules.EmptyStatementNotInLoop=true
options.pmd.rules.CloseConnectionRule=true
options.pmd.rules.DefaultLabelNotLastInSwitchStmt=true
options.pmd.rules.BooleanInstantiation=true
options.pmd.rules.UnusedPrivateField=true
options.pmd.rules.MethodNamingConventions=true
options.pmd.rules.AvoidDeeplyNestedIfStmts=true
options.pmd.rules.DontImportSunRule=true
options.pmd.rules.FinalFieldCouldBeStatic=true
options.pmd.rules.ConstructorCallsOverridableMethodRule=true
options.pmd.rules.EmptyIfStmt=true
options.pmd.rules.NullAssignment=true
options.pmd.rules.SuspiciousHashcodeMethodName=true
options.pmd.rules.JUnitSpelling=true
options.pmd.rules.UnnecessaryConstructorRule=true
pmd.customRulesPath= - CleanArchitecture-2020 . . . . 15 matches
The mistake that business managers and developers often make is to elevate items in position 3 to position 1.
It is the responsibility of the software development team (not business managers) to assert the importance of architecure over the urgency of features.
We find the system divided into decoupled horizontal layers - the UI, application-specific business rules, application-independent business rules, and the database.
The direction of this line shows that the Database does not matter to the BusinessRules, but the Database cannot exists without the BusinessRules.
The database could be implemented with Oracle, or MySQL, or even flat files. The business rules don't care at all.
== Ch20. Business Rules ==
Business rules are rules or procedures that make or save the business money.
Critical Business Rules
Critical Business Data
An object within our computer system that embodies a small set of critical business rules operating on Critical Business Data.
A use case describes application-specific business rules as opposed to the Critical Business Rules within the Entities.
Use cases contain the rules that specify how and when the Critical Business Rules within the Entities are invoked.
Use cases do not describe how the system appears to the user. Instead, they describe the application-specific rules that govern the interaction between the users and the Entities.
The business rules should be the most independent and reusable code in the system.
Another problem is that a layerd architecture doesn't scream anything about the business domain. - BusinessRuleEngine . . . . 9 matches
#keywords Business Rule Engine, drools, rule engine
Should I use a Rules Engine? - https://martinfowler.com/bliki/RulesEngine.html
[Some Guidelines For Deciding Whether To Use A Rules Engine]
https://stackoverflow.com/questions/775170/when-should-you-not-use-a-rules-engine - html5_book_원철연 . . . . 7 matches
== 1. CSS의 구조와 선택자(selector), 1.1 요소 이름을 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/481 ==
1.2 id를 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/482
1.3 class를 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/483
1.4 속성(Attribute)을 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기, 1.4.1 “[속성]”의 경우 http://fromyou.tistory.com/484
1.5 의사 클래스(pseudo-class)를 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/489
1.6 의사-요소(pseudo-element)를 이용한 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/499
1.8 모든 요소(Element)를 포함하는 선택자(Selector) 구성과 규칙(Rule) 만들기 http://fromyou.tistory.com/504 - PrestoAndHiveTrainingSession . . . . 5 matches
- DFS(HDFS, S3) > ResourceManager(YARN) > Processing(MapReduce,Tez) > SQL Engine(Hive)
- DFS(HDFS, S3) > ResourceManager(YARN) > Processing(SparkEngine) > SQL Engine(SparkSQL)
- DFS(HDFS, S3) > SQL Engine(Presto,Impala,Tajo)
basedOnMemory: SparkSQL(SparkEngine), Presto,Impala,Tajo - drools . . . . 5 matches
#keywords Business Rule Engine, drools
cf. [Some Guidelines For Deciding Whether To Use A Rules Engine] - MoniWiki . . . . 3 matches
#keywords MoniWiki, WikiEngine, GPL
MoniWiki is a PHP based WikiEngine. WikiFormattingRules are imported and inspired from the MoinMoin. '''Moni''' is slightly modified sound means '''What ?''' or '''What is it ?''' in Korean and It also shows MoniWiki is nearly compatible with the MoinMoin. - SomeGuidelinesForDecidingWhetherToUseARulesEngine . . . . 3 matches
#keywords Business Rule Engine, drools
http://www.jessrules.com/guidelines.shtml - eclipse-keys . . . . 2 matches
"Window","Show Ruler Context Menu","Ctrl+F10","Editing Text"
"Window","Show Ruler Context Menu","Ctrl+F10","Editing Text" - 코틀린마이크로서비스개발-후안안토니오 . . . . 2 matches
- 서비스 모델: IaaS(AWS, Google Compute Engine), Paas(Google App Engine), SaaS(Google G Suite, MS Office 365) - 1일차-SqlTuning교육 . . . . 1 match
RBO : Rule based Optimizer - BuildingMicroservices;마이크로서비스아키텍처구축-샘뉴먼지음,정성권옮김 . . . . 1 match
* business capability
- HATEOAS : Hypermedia As The Engine Of Application State - Cassandra . . . . 1 match
[Basic Rules of Cassandra data modelling] - EbXML등장배경 . . . . 1 match
1998년 XML 1.0이 발표된 이후 다양한 전자거래 표준(로제타넷, 커머스넷, eCo, 아리바등)이 등장하였다. XML의 가장 큰 장점은 확장성이다. 기존의 EDI가 사용되는 구문은 정해진 포맷을 사용하여 확장성을 허용하지 않았다. 수십개의 표준화 작업이 진행되고, 각각의 나름대로 서로 다른 프레임워크를 정의한다면, 상호연동성을 도모하는 것은 지극히 어여룽 작업이다. 이렇게 시장이 표준화와 배치되는 방향으로 나아가는 상황에서 XML 기반의 단일 표준화를 추진할 필요성을 인식하고 1999년 11월 국제 EDI 추진기구인 UN/CEFACT가 IT 민간 컴소시엄인 OASIS(Organization for the Advancement of Structured Information Standards)와 공동으로 1999년 11월 부터 18개월 동안 ebXML(e-Business using XML)이라는 체세대 인터넷 전자상거래 표준 프레임워크를 제정하였다. - HelpOnEditing . . . . 1 match
* HelpOnFormatting - general text formatting rules
* HelpOnRules - horizontal rules - HelpOnFormatting . . . . 1 match
== Text Formatting Rules == - HelpOnRules . . . . 1 match
== Horizontal Rules ==
You can insert a horizontal rule across the page by typing four or more dashes. The number of dashes in a horizontal rule markup determines how thick it is, up to a limit of 10.
--- (not a rule)
--- (not a rule) - Module04.S/WArchitecture . . . . 1 match
* Virtual machines : Interpreters, Rule-based systems - TheWinnerTakesItAll . . . . 1 match
Playing by the rules
Rules must be obeyed - WikiEngine . . . . 1 match
See Wiki:WikiEngine - WikiFormattingRules . . . . 1 match
Wiki:TextFormattingRules - WikiWyg . . . . 1 match
http://kwiki.org/?KwikiFormattingRules - apachetajo . . . . 1 match
DW VS QueryEngine :
